v3.1.0

Compare Source

Added

• Allow setting escape option per parameter replacing.
  For more security this should be used instead of disabling paramter escaping,
  see pull request #​756

  // Example
  t(
  	'my-app',
  	'{a}{userInput}{a_end}',
  	{
  		a: {
  			value: '<a>',
  			escape: false,
  		},
  		userInput: somePossiblyInsecureValue, // This will be escaped
  		a_end: {
  			value: '</a>',
  			escape: false,
  		}
  	},
  )

v3.0.1

Compare Source

Fixed

• Ensure that built type definitions are bundled with the release and located in the correct directory

v3.0.0

Compare Source

Full Changelog

Breaking changes

Instead of also sanitizing the replacing variables, now only the result is sanitized, see pull request #​648.

This will improve the performance if multiple placeholders are used and it allows this,
while the string is still sanitized:

t(
	'See {linkstart}documentation{linkend}',
	{
		linkstart: '<a ...>',
		linkend: '</a>',
	},
	// No number
	undefined,
	{
		// Do not escape the result as we want the HTML anchor element
		escape: false,
	}
)

Added

• feat: export aliases t and n for translate and translatePlural

Fixed

• fix!: Only sanitize the result string when replacing variables

Changed

• Update NPM to latest LTS v10
• Migrate to vite for transpiling and vitest for testing
• chore: Added more tests for special cases on plural forms
• chore(deps): Bump tough-cookie to 4.1.3
• chore(deps): Bump postcss to 8.4.31
• chore(deps): Bump @​nextcloud/typings to 1.8.0
• chore(deps): Bump dompurify to 3.1.1
• chore(deps): Bump @​nextcloud/router to 3.0.1